Mobile application for medication reminders

ABSTRACT

Methods, systems, and computer-readable media are provided for computer based healthcare information to automatically provide reminders to a patient to take prescription medications at the appropriate times on the patient&#39;s mobile device. The patient enters a medical record number (MRN) into the mobile device and this information is communicated to the patient&#39;s electronic medical record. The user device receives the prescription information for the MRN from the patient&#39;s electronic medical record. Utilizing the prescription information on the user&#39;s device, the user can view and set reminders to take the medication directly from the patient&#39;s mobile device.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Non-Provisional patentapplication Ser. No. 15/099,231, filed Apr. 14, 2016, entitled “MobileApplication for Medication Reminders”, the disclosure of which isincorporated herein by reference in its entirety.

BACKGROUND

Many readmissions to hospitals and clinics occur because patients arenot compliant with taking prescribed medications. Patients often forgetto take prescribed medicines on time. Additionally, mistakes can be madeby patients or caretakers in properly administering the single ormultiple medications at home at the right time.

There are medication reminder programs available for reminding patientsabout medication to be taken on time but all these programs require amanual set up of reminders by keying information's like medication name,dose, drug form, admiration route, frequency, start and stop date time.This can be time consuming activity and can lead to wrong input ofinformation resulting in reminding a patient to take a wrong medicationand/or at wrong time.

SUMMARY

The mobile application described provides patient with continuity ofcare post discharge by facilitating the receipt of latest prescriptionfrom an electronic medical record database, such as Cerner Millenniumdatabase, by sending MRN (Medical Record Number) as requested. Theinformation received at the user device from the patient's electronicmedical record includes the medications prescribed along with detailsthat are required to set reminders for the patient to take themedication. The consumer of the application can have look at eachmedication detail and set reminder for each one of them or collectivelyset reminder for all medications by single touch on ‘Set Reminder’ icon,this action sets the reminder in an alarm manager component. Thereminder can also be removed from the alarm manager component byclicking on the Alert icon. Thus, the availability of informationrequired to set reminder eliminates even the remote possibility ofmaking mistakes as compared to manually input of information. Theapplication users a connection with internet through Wi-Fi or mobiledata.

Hospitals/clinics that use an electronic medical record database, suchas Cerner Millennium Solutions like PowerOrders, to prescribeprescriptions to patient during discharge process can also make sure thecontinuity of care post discharge by sending the prescription details topatient on demand using CareRemind application. Thus adding value to theservices provided to Hospitals/clinics and its patients.

An electronic medical record database, such as Cerner Millenniumdatabase, will have the prescriptions ordered by physician for thepatients. The user needs to provide the MRN via a user device which willbe sent to the database. The database will send the latest prescriptionfor the MRN as a message back to the user device. The user is notifiedabout the message. The details can be viewed and reminder can be set.The application then notifies the user with the reminder at scheduleddate and time which the user acknowledges by taking or skipping themedication. All the acknowledgment are stored and maintained as logwhich the user can view.

The claimed solution is necessarily rooted in computerized electronicmedical record technology in order to overcome a problem specificallyarising in the realm of computer healthcare information networks, andthe claims address the problem of efficiently and correctly providingmedication information and reminders to a patient on the patient'smobile device. If adhering to the routine, conventional function ofsetting medication reminders, a patient would manually enter, such astyping in, each medication and medication information and manually set areminder on the user's device. This can cause delay and for theincorrect information to be entered.

The claimed invention overcomes the limitations of current computerhealthcare information technology and provides other benefits that willbecome clear to those skilled in the art from the foregoing description.

The claimed system and method of the present application represents anew paradigm of providing medication information and reminders onpatient's mobile device. Not only does the claimed invention easilyprovide medication information and reminders to a patient without manualentry but it also prevents errors in entry of the information and savesthe user significant time. Users of electronic medical records orelectronic health records utilizing the claimed invention will noticeincreased performance of their EMR or EHR, increased retrieval of themedication information from storage, fewer user steps to utilize the EMRand user access to the medication information. Furthermore, anythingthat reduces the number of “clicks” or entries a computer or mobiledevice user has to make in an EMR or EHR or to enter medicationreminders results in reducing the memory utilization, CPU cycles, numberof operations that need to be performed by the computer, and powerconsumption. The resulting cost savings and operational efficiencies ofa computer electronic medical record magnify the potential benefits ofthis technology.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary computing environment suitableto implement embodiments of the present invention;

FIG. 2 is an exemplary system architecture suitable to implementembodiments of the present invention;

FIG. 3 is a flow diagram depicting embodiments of the present invention;and

FIGS. 4-19 are graphical user interface depictions of user flow to setup medication reminders on a user device in accordance with embodimentsof the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent elements of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention are directed to methods, systems,and computer-readable media for a system and method for mobile deviceusers to communicate with an electronic medical or health record and toefficiently and simply set up medication reminders on their mobiledevice without having to manually input information into their mobiledevice. The user's mobile device communicates the medical record number(MRN) as request to an electronic medical record service, such as CernerMillennium database, and the database communicates the latestprescription information for the user in response to the request. Onreceiving the prescription message back in mobile, the user can reviewdetailed information regarding the medication and set the reminder bysingle touch or click on the set reminder icon. A user can also setreminders for all medication based on prescription date.

An exemplary computing environment suitable for use in implementingembodiments of the present invention is described below. FIG. 1 is anexemplary computing environment (e.g., medical-informationcomputing-system environment) with which embodiments of the presentinvention may be implemented. The computing environment is illustratedand designated generally as reference numeral 100. The computingenvironment 100 is merely an example of one suitable computingenvironment and is not intended to suggest any limitation as to thescope of use or functionality of the invention. Neither should thecomputing environment 100 be interpreted as having any dependency orrequirement relating to any single component or combination ofcomponents illustrated therein.

The present invention is a special computing system that can leveragewell-known computing system environments or configurations. Examples ofwell-known computing systems, environments, and/or configurations thatmight be suitable for use with the present invention include personalcomputers, server computers, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

The present invention might be described in the context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Exemplary program modules comprise routines,programs, objects, components, and data structures that performparticular tasks or implement particular abstract data types. Thepresent invention might be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules might be located in association with localand/or remote computer storage media (e.g., memory storage devices).

With continued reference to FIG. 1 , the computing environment 100comprises a computing device in the form of a control server 102.Exemplary components of the control server 102 comprise a processingunit, internal system memory, and a suitable system bus for couplingvarious system components, including data store 104, with the controlserver 102. The system bus might be any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, and a local bus, using any of a variety of bus architectures.Exemplary architectures comprise Industry Standard Architecture (ISA)bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus,Video Electronic Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus, also known as Mezzanine bus.

The control server 102 typically includes therein, or has access to, avariety of non-transitory computer-readable media. Computer-readablemedia can be any available media that might be accessed by controlserver 102, and includes volatile and nonvolatile media, as well as,removable and nonremovable media. By way of example, and not limitation,computer-readable media may comprise computer storage media andcommunication media. Computer storage media includes both volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by control server 102. Communication media typicallyembodies computer-readable instructions, data structures, programmodules or other data in a modulated data signal such as a carrier waveor other transport mechanism and includes any information deliverymedia. The term “modulated data signal” means a signal that has one ormore of its characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer-readable media.

The control server 102 might operate in a computer network 106 usinglogical connections to one or more remote computers 108. Remotecomputers 108 might be located at a variety of locations in a medical orresearch environment, including clinical laboratories (e.g., moleculardiagnostic laboratories), hospitals and other inpatient settings,veterinary environments, ambulatory settings, medical billing andfinancial offices, hospital administration settings, home healthcareenvironments, and clinicians' offices. Clinicians may comprise atreating physician or physicians; specialists such as surgeons,radiologists, cardiologists, and oncologists; emergency medicaltechnicians; physicians' assistants; nurse practitioners; nurses;nurses' aides; pharmacists; dieticians; microbiologists; laboratoryexperts; laboratory technologists; genetic counselors; researchers;veterinarians; students; and the like. The remote computers 108 mightalso be physically located in nontraditional medical care environmentsso that the entire healthcare community might be capable of integrationon the network. The remote computers 108 might be personal computers,servers, routers, network PCs, peer devices, other common network nodes,or the like and might comprise some or all of the elements describedabove in relation to the control server 102. The devices can be personaldigital assistants or other like devices.

Computer networks 106 comprise local area networks (LANs) and/or widearea networks (WANs). Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets, and the Internet.When utilized in a WAN networking environment, the control server 102might comprise a modem or other means for establishing communicationsover the WAN, such as the Internet. In a networking environment, programmodules or portions thereof might be stored in association with thecontrol server 102, the data store 104, or any of the remote computers108. For example, various application programs may reside on the memoryassociated with any one or more of the remote computers 108. It will beappreciated by those of ordinary skill in the art that the networkconnections shown are exemplary and other means of establishing acommunications link between the computers (e.g., control server 102 andremote computers 108) might be utilized.

In operation, an organization might enter commands and information intothe control server 102 or convey the commands and information to thecontrol server 102 via one or more of the remote computers 108 throughinput devices, such as a keyboard, a microphone (e.g., voice inputs), atouch screen, a pointing device (commonly referred to as a mouse), atrackball, or a touch pad. Other input devices comprise satellitedishes, scanners, or the like. Commands and information might also besent directly from a remote healthcare device to the control server 102.In addition to a monitor, the control server 102 and/or remote computers108 might comprise other peripheral output devices, such as speakers anda printer.

Although many other internal components of the control server 102 andthe remote computers 108 are not shown, such components and theirinterconnection are well known. Accordingly, additional detailsconcerning the internal construction of the control server 102 and theremote computers 108 are not further disclosed herein.

In an embodiment exhibited by FIG. 2 , the processing duties are splitamong several computing systems. The data store 210 may be implementedthrough a database system and may be an electronic medical record orelectronic health record. The internet serves as a communications linkto consumer mobile devices. The tasks performed by the processor utilizea variety of computer technology. In one embodiment, the technology canbe divided into three tiers, web server, application server and databaseserver. Each tier is comprised of a number of system layers as describedbelow.

Prescription Reminder Manager

Prescription reminder manager 275 is the control center for consumers,such as patients or family members. Prescription reminder manager 275resides on a personal computing device or mobile device 205 (such asmart phone) of the consumer. Furthermore, consumer manager 275 has acalendar interface 245 with device 205 such that manager 275 can receiveinformation from the Alarm Manager component residing or connected todevice 205.

The prescription reminder manager 275 allows the consumer to communicatewith the patient's electronic medical records 210 via a network. Thepatient or patient representative may initiate request for receivingmedication information from the device 205 via user interface 225. Thepatient identification 230 (Medical Record Number) can be transmitted toan EMR via the EMR interface 235 such that the correct EMR for thepatient is utilized.

The prescription reminder manager 275 maintains a user interface 225with the consumer, patient identification 230 and an API layer betweenthe patient's electronic medical record 210 and the prescriptionreminder manager 275.

The prescription reminder manager 275 is able to maintain additionalpatient information such as prescription information for the patientmaintained by the prescription list engine 240. The device 205 havingthe prescription reminder manager 275 has access to AlarmManager,component which is supported on android smart phones, or personalcomputers. Prescription reminder manager 275 user interface forproviding the consumer with a prescription list 240 (discussed in detailbelow) and information regarding the consumer's medications. A consumercan access known medication information via an interface 225 displayedby the prescription reminder manager 275 on the consumer's smart phoneor personal computer 205.

Prescription Reminder Manager

Prescription Reminder Manager 275 (CareRemind) is comprised ofsubcomponents including user interface 225, Patient identification 230,electronic medical record interface 235, calendar interface 245,prescription list engine 240 and prescription log database 250. It willbe appreciated that some or all of subcomponents of prescriptionreminder manager 275 may be accessed via a network and reside on or moredevices remote to consumer device 205. Prescription reminder manager 275is configured to be used by a consumer, such as a patient, to configurereminders for the patient to take medication as prescribed.

The prescription reminder manager 275 is also in directly or indirectlyin communication with one or more electronic medical record databases210.

User Interface 225

User interface 225 is in communication with prescription remindermanager 275. Prescription reminder manager 275 communicates patientidentification 230 (MRN) to EMR 210. User Interface 225 receives MRN asinput by the consumer using device 205. User interface 225 communicatesand displays medication information and medication reminders generatedby the prescription list engine 240.

EMR Interface

Electronic Medical Database 210 is in communication with prescriptionreminder manager 275 via EMR interface 235. Electronic Medical Database210 receives the MRN number entered by the user from prescriptionreminder 275 of device 205. Electronic Medical Database 210 accessespatient records 255 to obtain medication information for the MRN number.Electronic Medical Database 210 then communicates the information viathe EMR interface 235 to prescription reminder manager 275 such that themedication information can be provided to the consumer via userinterface 225 of device 205.

Prescription List Engine

The prescription list engine then maintains a list of the patient'sprescription received from the Electronic Medical Database 210 andarranges the medications according to date prescribed for display to theuser. For example, medication attributes include:

Name of the medication including brand name, generic name, chemicalname.

Route that the medication is to be administered (e.g., oraladministration, nasal administration, ocular administration)

Frequency refers to how often the medication is to be administered tothe patient (e.g., once a day, every 4 hours, as needed).

Length refers to how long the medication is to be administered orprescription should last (e.g., 10 days, 12 hours)

Dosage is the amount and strength of the medication that is to beadministered (e.g., 2 pills, 2 drops, 5 cc)

Special instructions provided by the clinician such as “take with food,take at night.”

Date Prescribed is the date the medication was prescribed.

Prescribing Clinician is the name, address, clinician identifier and DEAnumber if needed.

Pharmacy fulfilling medication order is the name, pharmacy identifierthat has filled the prescription.

Codes and coding information associated with the medication and theabove information.

Information regarding physical characteristic of the medicationincluding color, size, markings and textual codes etched on themedication.

Information for each medication such as drug interactions, adverseevents and black box warnings.

Prescription list engine 240 leverages information received from thepatient record to maintain a running list of medications and associatedmedication information for the patient associated with the MRNs entered.For example, when consumer uses a first MRN, the MRN is transmitted,decoded and matched by the electronic medical record database 210.Medication associated with the MRN and related information is maintainedin in the prescription list engine. The following example, has onemedication associated with the MRN entered on the user device and isadded to a medication list using prescription list engine 240. However,it will be appreciated there may be multiple medications and associatedmedications associated with a single MRN, and the medications andassociated information is maintained by the prescription remindermanager 275 under a band level for the MRN (and date prescribed).Medication name followed by ‘Set Reminder’ icon is displayed under theband level.

John Doe Medication List

MRN 12345

Medication 1

On long press over the medication name the attributes will be displayedas described under 0037.

Based on the medication list, if the user requests a reminder formedication 1 (as discussed in more detail below with respect to FIGS.4-19 ), the prescription list engine 240 creates reminder requests forthe medication and the start date and time for medication. For example,if the user requests a reminder for amoxicillin to start at 10:00 am onFeb. 2, 2016, the prescription list engine would generate reminderrequests for the amoxicillin at 10:00 am, 6:00 pm and 2 a.m. for theamoxicillin for each of 10 days starting on Feb. 2, 2016. These reminderrequests are communicated to the user device's Alarm Manager componentvia calendar interface 245. The requests are logged by the Alarm Managercomponent. When it is time for a reminder, the Alarm Manager componentcommunicates the reminder to the prescription list engine 240 viacalendar interface and the prescription reminder manager 275 displaysthe reminder using the user interface 225. The reminder may also beaccompanied by an audible alarm, buzzing and flashing lights dependingon the user's preference.

Prescription Log Database

After the prescription list engine displays the reminder to the user viauser interface 225, the user can select to mark the medication as‘taken’ or ‘skipped’. All of the user acknowledgements are stored andmaintained by the prescription log database 250 of prescription remindermanager 275 as a log. The log is viewable by the user by selecting toview the log for a medication (as shown below in FIG. 19 ). The user cannavigate through the dates for the medication using the navigationbuttons to navigate dates backward and forward. The information isdisplayed in the log includes date of prescription, the MRN, followed bymedication name followed by time when the notification was acknowledgeas taken or skipped. In one embodiment, the log can be provided by theuser to an authorized third party.

Electronic Medical Record Database

Electronic Medical Record Database 210 is computer store containinghealthcare information for individual patients. EMR 210 includes anelectronic version of patient records including information for thepatient, such as medication and infusion orders, tasks, images,examination reports, testing and lab results, medical history, andprescription information including medical record number (MRN). EMR 210contains the standard medical and clinical data gathered in a provider'soffice. An EMR 210 is a digital or computerized version of a paper chartthat contains all of a patient's medical history. In the embodiments ofthe present invention, the patient identifier 230 is stored in the EMRfor the individual patient. Additional, medication names, dosage, routeand frequency are stored in the patient's EMR associated with a medicalrecord number.

EMR 210 is also in communication via clinician interface 270 andpharmacy interface 265 with one or more clinician devices 215 andpharmacy applications 220. The clinician inputs information for thepatient via clinician device which is communicated to the EMR via anetwork. The pharmacy application also contains information regardingthe prescription for the patient. Information from the pharmacy fillingthe medication(s) can be included in the medical record information(such as pharmacy name, phone number and link to electronically refillmedication.)

System Flow

The prescription reminder manager acts as a clearinghouse for allmedications for patient to provide a patient with a quick and accuratepicture of their medications. The system maintains a real-time interfacewith patient/consumer and generating medication lists for access by thepatient and generating reminders for the patient to take his or hermedications. The flow chart of FIG. 3 shows how the distinctive featurewhich provides user with the facility to send request for latestprescription, set the reminder in mobile and elementary feature whichreminds user about the medication to be taken, which is acknowledged byuser and can be viewed as log.

Referring to FIG. 3 , the system flow 300 of the prescription remindermanager application is depicted. The user is typically registered alongwith the mobile device number at the clinic/facility/hospital during thevisit at 305. The consumer (typically the patient) loads to prescriptionreminder manager application at step 310. This activation is typicallyaccomplished by logging into prescription reminder manager applicationby the consumer.

Consumer enters an MRN number that they have received duringregistration or upon discharge from a hospital or clinic. Theprescription reminder manager transmits MRN to the electronic medicalrecord database at 320. The information from the MRN can be translatedinto a medication and medication for the patient's medication list bythe electronic medical record database.

The medication(s) and medication information associated with the MRN arecommunicated from the electronic medical record database to theprescription reminder manager which receives and loads the prescriptioninformation for the MRN to the user device at step 325. Multiple MRNsmay be entered by the user and the associated information iscommunicated back to the user device for each of the MRNs.

Consumer requests the prescription reminder manager application set areminder for one or more of the medications at step 330. The reminder(s)are generated by the prescription reminder manager application and arecommunicated to the Alarm Manager component of the user device at step335. At the appropriate time, the Alarm Manager component notifies theprescription reminder manager application of the reminder and theprescription reminder manager application displays the reminder to theuser via the user device at step 340. The user acknowledges whether themedication has been taken or skipped by selecting the appropriate iconon the user device and this is logged by the prescription remindermanager application at step 345. If the user does not acknowledge thereminder, in one embodiment, the prescription reminder managerapplication logs the reminder as ‘skipped’ and/or ‘not acknowledged’ atstep 345. In some embodiments, the user can make changes to the log ofthe medication if they have forgotten to acknowledge that a medicationhas been taken.

FIGS. 4-19 , as described in more detail below, show embodiments of thepresent invention including the functionality and user interaction withdisplay screens.

FIG. 4 illustrates the medication reminder screen (CareRemind) homescreen. There are three different types of actions that the user cantake by interacting with the home screen of FIG. 4 including: (1)receiving a reminder (2) viewing a prescription and (3) viewing logs.

Upon a user selecting choosing the ‘Receive Reminder’ action from atouch screen or by clicking on an icon, a screen as shown in FIG. 5 isdisplayed in which the user can input his/her MRN (Medical RecordNumber) and click on submit button to send request from the consumerdevice to the electronic medical record database such as the CernerMillennium database. The submit button is enabled when MRN field isprovided with value.

After the user inputs the MRN and submits, a message ‘MRN SendSuccessfully’ is displayed to user is displayed in FIG. 6 on theconsumer device indicating that the request was successfully from themobile device to the electronic medical record database.

Upon receiving latest prescription as response from the electronicmedical record database to the mobile device, the user is notified withan icon being displayed in the notification bar on top of the mobiledevice screen as shown in FIG. 7 . In this embodiment, the notificationis depicted as a “+” in the upper left corner but it will be appreciatedthat any notification mechanism may be displayed in any location.

On the user's selection of the icon in the notification bar either bytouch or clicking on the icon, the icon along with the message and time(i.e., time when the message was received) is displayed as shown in FIG.8 . The ‘Prescription’ screen can be opened by the user by clicking onthe message “Prescription Received!” shown in FIG. 8 . Alternatively,the ‘Prescription’ screen can be accessed by the user selecting the‘View Prescription’ action button from the home page as shown in FIG. 4.

Referring next to FIG. 9 , the display of the prescriptions for the userassociated with the input MRN are displayed on the mobile device screenand in this embodiment, are displayed in a band for each prescriptionorder date. The prescriptions are ordered in the display in descendingorder, e.g., the most recent prescription is at the top of the list.Prescriptions that have not expired for the patient are listed on thescreen. Notifications as shown in FIG. 8 , are displayed when the MRN isentered and sent as a request to the electronic medical record database.The user will not typically receive multiple notifications for a singleMRN using this application.

In FIG. 9 , the patient has prescription bands for Aug. 25, 2015, Aug.15, 2015 and Oct. 7, 2015. The band can be selected to expand orcollapse the viewing list of items prescribed on that date as shown inFIG. 10 . An icon for “set reminder” is displayed next to eachprescription name and at each band level.

A user can select to set reminders for individual prescriptions listed.For example, in FIG. 9 , the user may select to set a reminder for anindividual prescription by selecting the “set reminder” icon displayednext to the name of the prescription. Alternatively, the user may selectthe “set reminder” icon at the band level for all prescriptions orderedon the date of the band (e.g., for the MRN entered). For example, theuser can select the set reminder icon for all prescriptions ordered onJul. 10, 2015 at the band level.

The selection of the “set reminder” icon for a particular prescriptionor at the band level sets a reminder in the Alarm Manager component ofthe mobile device. Reminder setting for prescriptions and at the bandlevel is discussed in more detail below with reference to FIGS. 13 and14 . Expired prescriptions are removed from prescription list displayedin FIG. 9 , upon expiration or the stop/end date for administering themedication.

Referring next to FIG. 12 , the user may view more detailed informationfor each prescription in the prescription list. This is done by a longpress or selection of the user on the prescription list of FIG. 9 . FIG.12 depicts the screen with detailed information for a prescriptionmedication. If the user wishes to return to the prescription list screenof FIG. 9 , the user selects the back button shown on the bottom left ofFIG. 12 . The detailed information for the prescription includesstrength dose, dose unit, drug form, administration route, frequency anddescriptions and instructions as shown in FIG. 12 . Additionalinformation for the prescription may also be displayed includingpharmacy information such as name and phone number, a button to refillthe medication, refill reminders, warnings and instructions for thepatient included in the prescription (e.g., take with food, do not mixwith alcohol).

Referring next to FIGS. 13 and 14 , reminders for medications can be setby the user two ways. First, the user can set a reminder for allmedication prescriptions at the band level by selecting the ‘SetReminder’ icon at the band level as shown in the screen design above forthe prescription dated 25 Aug. 2015 and Oct. 7, 2015. Upon selection,the icon at the band level changes from ‘Set Reminder’ to ‘Alert’ at theband level when all the medications under the prescriptions are set asreminder as shown with reference to the prescription band level datedAug. 25, 2015 in FIG. 13 and FIG. 14 . In addition, the icon for each ofthe medications under the band level is changed from the ‘Set Reminder’icon to the ‘Alert’ icon. In addition a reminder is set in the AlarmManager component of the user device for each of the respectivemedications from its start date/time to end date/time and a notification“reminder set” message is displayed to indicate that the reminder hasbeen set for the user. If the entire band level is not set for reminder,the icon at the band level does not change at the band level for examplefor the prescription band level dated Aug. 15, 2015.

The user can set a reminder for individual medication instead of at theband level by selecting the ‘Set Reminder’ icon at the medication levelas shown in the screen design of FIGS. 13 and 14 for the medicationacetaminophen for in the prescription band level for Aug. 15, 2015. Uponselection, the icon at the medication level changes from ‘Set Reminder’to ‘Alert’ at the medication level as shown with reference to themedication acetaminophen dated Aug. 15, 2015 in FIG. 13 and FIG. 14 . Inaddition a reminder is set in the Alarm Manager component of the userdevice for the medication from its start date/time to end date/time anda notification “reminder set” message is displayed to indicate that thereminder has been set for the user.

Referring next to FIGS. 15 and 16 , the user has the ability to removereminders from the Alarm Manager component. First, once the reminder isset at the band level, the user selects or clicks on the ‘Alert’ iconagain at band level, all the reminders will be removed from AlarmManager component for medications at a time (for the given prescriptionband level). The icon then changes back to ‘Set Reminder’ icon at theband level and for each of the medications as shown in FIGS. 15 and 16 .

For reminders set for individual medications, the reminder can beremoved from the Alarm Manager component for the individual medicationsby selecting or click on the ‘Alert’ icon again the reminder forindividual medications. The icon for the medication then changes back to‘Set Reminder’ icon. If all reminders for medications individually areremoved, the respective prescription icon changes from the ‘Alert’ iconto the ‘Set Reminder’ icon at the band level as shown in FIGS. 15 and 16. Additional, the user is notified on removing the reminder from theAlarm Manager component as shown in FIG. 16 .

Referring next to FIG. 17 , medication reminders are set leveraging theAlarm Manager component of a mobile device, such as a smart phone orandroid device. As discussed above, the prescription reminder manageruses the Alarm Manager component available within the mobile device toreceive notifications about alerts. For example, there is a reminder seton the Alarm Manager component to alert user at LOAM for Aspirin theprescription reminder manager will receive this alert from the AlarmManager component. On receipt of this alert, the prescription remindermanager will update the status bar of mobile device. User touches thenotification take further action.

FIG. 17 is a representation a medication reminder screen (medicationreminder screen). The medication reminder screen is displayed on theuser device when the user touches or selects the notification icon inthe notification bar of the mobile (as shown in FIG. 7 ).

The medication reminder screen as shown in FIG. 17 displays thefollowing information:

Time Followed by Day and Date

Skip icon that can be selected by user to skip the medication

Taken icon that is selected by user to acknowledge the medication astaken

Snooze icon that is selected by user to postpone the reminder byselecting the snooze time. The reminder will be displayed to user afterthe snooze time. The user can select the snooze time in differentincrements such as 5/15/30/45/60 minutes.

Medication Name Followed by Dose

Referring next to FIG. 18 , an Action Summary Window is shown. TheAction Summary Window displays a summary of the action that has beentaken on the medication reminder screen. FIG. 17 displays the summarywhen a user clicks/touches the Taken button in the medication reminderscreen. The acknowledged reminders (i.e., reminder marked as taken orskipped) are stored as logs in the mobile database of the medicationreminder manager which are discussed with more detail below withreference to FIG. 18 .

FIG. 19 displays to the user current log information. The user cannavigate through dates using the navigation buttons to navigate datesbackward and forward. The information is displayed in the log includesdate of prescription, the MRN, followed by medication name followed bytime when the notification was acknowledge as taken or skipped.

Each schedule dose of medication for each medication is listed as logafter user acknowledges the notification as taken or skipped. User candownload or electronically transfer the logged information as they seefit to give to their clinician, pharmacy or caregiver as a record oftheir medication compliance/non-compliance.

The present invention has been described in relation to particularembodiments, which are intended in all respects to be illustrativerather than restrictive. Further, the present invention is not limitedto these embodiments, but variations and modifications may be madewithout departing from the scope of the present invention.

1. A system useful in a computer healthcare system serving medicationreminders to a patient, the system comprising: (a) a computer processoron an individual's computing device programmed to: (i) receiving from anindividual's electronic medical record identification of a one or morefirst medications and a reminder time and date for the one or more firstmedications; (ii) presenting the one or more first medications on aninteractive screen on the individual's computing device; (iii)presenting a reminder icon simultaneously with the one or more firstmedications and the reminder time and date for the one or more firstmedications on the interactive screen on the individual's computingdevice; (iv) in response to receiving a selection of the reminder iconon the interactive screen, requesting to set a medication reminder totake the one or more first medications on the individual's computingdevice; (v) automatically communicating the reminder time and date to analarm manager component of the individual's computing device; (vi)automatically at the reminder time and date receiving from the alarmmanager component an indication to present the medication reminder;(vii) presenting the medication reminder on the interactive screen onthe individual's computing device; and (viii) in response to receiving aselection of the reminder icon on the interactive screen, changing thereminder icon to an alert icon on the interactive screen.
 2. The systemof claim 1, further comprising presenting simultaneously on theinteractive screen a skip icon simultaneously with the medicationreminder, wherein the skip icon indicates the one or more firstmedications have been skipped.
 3. The system of claim 2, furthercomprising receiving from the interactive screen a selection of the skipicon indicating the one or more first medications have been skipped. 4.The system of claim 1, further comprising presenting simultaneously onthe interactive screen a snooze icon simultaneously with the medicationreminder, wherein the snooze icon indicates an increment of time topostpone the medication reminder.
 5. The system of claim 4, furthercomprising: receiving on the interactive screen a selection of thesnooze icon; and postponing the medication reminder for the increment oftime.
 6. The system of claim 1, further comprising receiving from theinteractive screen an indication the one or more first medications havebeen taken or skipped.
 7. The system of claim 6, further comprising:creating a first database record for the one or more first medications;and automatically updating the first database record with the indicationthat the one or more first medications have been taken or skipped. 8.The system of claim 1, further comprising receiving from the interactivescreen a request to delete the medication reminder for the one or morefirst medications.
 9. The system of claim 8, further comprising:creating a first database record for the one or more first medications;and updating the first database record to delete the medication reminderto take the one or more first medications.
 10. The system of claim 1,simultaneously displaying on the interactive screen the alert icon andthe one or more first medications and the reminder time and dates forthe one or more first medications.
 11. The system of claim 1, whereinreceiving from the patient's electronic medical record further comprisesreceiving a frequency and a duration for each of the one or more firstmedications.
 12. The system of claim 11, further comprising generatingthe reminder time and date based on the frequency and the duration ofthe one or more first medications.
 13. One or more computer storagemedia having computer-usable instructions that, when used by one or morecomputing devices, cause the one or more computing devices to perform amethod serving medication reminders to a patient, the method comprising:(i) receive from an individual's medical record identification of a oneor more first medications and a reminder time and date for the one ormore first medications; (ii) presenting the one or more firstmedications on an interactive screen on an individual's computingdevice; (iii) presenting a reminder icon simultaneously with the one ormore first medications and the reminder time and date for the one ormore first medications on the interactive screen on the individual'scomputing device; (iv) in response to receiving a selection of thereminder icon on the interactive screen, requesting to set a medicationreminder to take the one or more first medications on the individual'scomputing device; (v) automatically communicating the reminder time anddate to an alarm manager component of the individual's computing device;(vi) automatically at the reminder time and date receiving from thealarm manager component an indication to present the medicationreminder; (vii) presenting the medication reminder on the interactivescreen on the individual's computing device; and (viii) in response toreceiving a selection of the reminder icon on the interactive screen,changing the reminder icon to an alert icon on the interactive screen.14. The media of claim 13, further comprising: receiving from theinteractive screen an indication the one or more first medications havebeen taken or skipped.
 15. The media of claim 14, further comprising:creating a first database record for the one or more first medications;and automatically updating the first database record with the indicationthat the one or more first medications have been taken or skipped. 16.The media of claim 13, further comprising: receiving from theinteractive screen a request to delete the medication reminder for theone or more first medications.
 17. The media of claim 16, furthercomprising: creating a first database record for the one or more firstmedications; and updating the first database record to delete themedication reminder to take the one or more first medications.
 18. Themedia of claim 13, wherein receiving from the patient's electronicmedical record further comprises receiving a frequency and a durationfor each of the one or more first medications.
 19. The system of claim18, further comprising generating the reminder time and date based onthe frequency and duration of the one or more first medications.
 20. Themedia of claim 13, simultaneously displaying on the interactive screenthe alert icon and the one or more first medications and the remindertime and dates for the one or more first medications.